5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
- Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 2-1: Data Dictionary Overview

Characteristics of the Data Dictionary


There are four principal attributes that characterize the APPX data dictionary. The dictionary is:

Active, in that its specifications are used by, and place real time restrictions on, both designers creating applications and users operating them. An active data dictionary maximizes consistency, productivity, and integration. It minimizes the chance for error, both when designing and using applications. For example, assume you have defined a numeric, five-character zip code field. APPX uses the length specification to provide a proper mask for the designer who is painting the field on an input image. APPX also uses data dictionary specifications as a basis for data validation when the image is executed. The system displays an error message if the application user attempts to enter a Canadian postal code (containing letters) into the numeric zip code field.

Processed, to enhance performance. The specifications you enter into the data dictionary are translated into a format more directly usable by APPX during process execution. Processing the data dictionary also searches for logic errors (invalid key definitions or illegal record lengths, for example), constructs default value records for each file, computes field lengths, and establishes the starting position for each field within a record. Refer to Processing the Data Dictionary for more information.

Internally documented. The dictionary provides entry screens for the online help text and printed technical documentation. Documentation is an integral part of APPX development and user interface.

Automatically monitored for structural changes, to ensure integrity.If you make such a change to the dictionary, all processes that reference changed elements are automatically updated, including images and event points. APPX flags existing data files that require restructuring, and permits you to automatically convert them to the new structure with the restructure utility in file management.

Application Design Manual                                         "Powered by Appx Software"

107

©2006 By APPX Software, Inc. All Rights Reserved